File naming for Mars 2020 data products

Instrument identifier, as shown in the table below.

This value can represent a color flag or a filter, illumination, or cover state.

For all color cameras, the flag is set based on the color space depending on whether the product is a 3-band product, or an individual band.

Only “E”, “F”, or “M” or Filter/LED can appear in EDRs. For Bayered images, the filter is replaced by the color flag at the debayering step.

For PIXL, the flag can be set based on the LEDs used to illuminate the target.

For ZCAM and SHERLOC Imaging the flag can be filter or cover state.

Special Processing flag, applicable to RDRs only. EDRs always have "_".

The special processing character is used to indicate off-nominal or special processing of the image. Examples include use of different correlation parameters, special stretches to eliminate shadows, reprocessing with different camera pointing, etc.

The meaning of any individual character in this field (other than "_" which means nominal processing) will be defined on an ad-hoc basis as needed during the mission. Within one Sol or a range of sols, the character will be used consistently. So, this field can be used to group together all derived products resulting from one kind of special processing. An attempt will be made to maintain consistency across different sols as well, but this may not always be possible; thus the meaning of characters may change across different individual or ranges of sols.

A database will be maintained containing all special processing designators that are used, the sols they relate to, and a description of the special processing that was done. This information is included in Appendix G of the camera data product SIS.

For surface operations, this field stores the four-integer Sol (Mars solar day) of the first (lowest clock time) acquired instrument data.

For cruise and ground test venues, refer to the camera data product SIS.

Mission venue identifier.

For surface operations, this field stores the 10-integer spacecraft clock count (SCLK, seconds). Which specific SCLK count (Start or End) is used depends on the instrument, but nominally it is the starting count of the first (i.e., lowest Clock time) acquired instrument data.

For ZCAM/SHERLOC Video Sequence, the Secondary Timestamp + Milliseconds for ith frame is computed as follows: First_Frame_SCLK + framerate * i.

Frame rate calculation (as in MSSS M2020 Camera Common Command):

frametime = 1/sysclk*(400*(2*vflush+ul_y+lines)+(lines*1648*4))+exposure

framerate = 1/(frametime+interval)

where

This equation only applies if the video exposure mode is not being used.

For cruise and ground test venues, refer to the camera data product SIS.

Underscore for readability. Always set to “_”. For single-frame meshes using this naming convention, the value is set to a code indicating the type of geometry used for the mesh: M = masked XYZ; X = unmasked XYZ.

Linearization flag:

Note that on Mars 2020 there is no "nominal" linearization as on other missions. All linearization is actual, so we use "L" as the flag. All EDRs are Raw geometry (“_”).

Thumbnail flag

Site identifier. Site location count from the RMC where the data were acquired.

Drive identifier. Drive count (position within a Site location) from the RMC where the data were acquired.

Identifies sequence ID or Round-Trip Tracking token (RTT).

Sequence-ID : Identifier indicating the command sequenced the image was acquired from. Specific values will be assigned by the uplink team.

RTT : Unique identifier used for tracking activities. Used in filename for PIXL only.

Note: All cameras will have an RTT associated with their images but not included in the filename. PIXL is a special case where RTT and PMC are required for filename uniqueness.

Camera-specific identifier. Each instrument has a unique format.

Format key:

Downsample resolution identifier. This value (n) indicates the level of downsampling applied to the image by the following equation: Resolution = 2ⁿ x 2ⁿ.

Compression type identifier. There are several modes of compression available, varying per instrument. The uplink team will decide which algorithm will provide the best results on a per sequence basis.

Identifier for the institution/team that created the product.

Product version number. In general, the highest number version represents the best version of a given product.

File extension; may be two, three, or four characters long.

Instrument identifier, as shown in the table below.

Instrument Configuration, an operational attribute of the Instrument that assists in characterizing the data.

EDRs always have "_".

For surface operations, this field stores the four-integer Sol (Mars solar day) of the first (lowest clock time) acquired instrument data.

For cruise and ground test venues, refer to the camera data product SIS.

Mission venue identifier.

For surface operations, this field stores the 10-integer spacecraft clock count (SCLK, seconds). Which specific SCLK count (Start or End) is used depends on the instrument, but nominally it is the starting count of the first (i.e., lowest Clock time) acquired instrument data.

For cruise and ground test venues, refer to the camera data product SIS.

Product Type identifier.

This field has the following rule-of-thumb:

Beginning “E” - Type of EDR, which is the first-order product with no processing

applied, with the exception of decompression in the case that Instrument applied

onboard compression.

If no beginning “E”, then product is an RDR.

Valid values for Product identifiers are listed below for EDRs

Site identifier. Site location count from the RMC where the data were acquired.

Drive identifier. Drive count (position within a Site location) from the RMC where the data were acquired.

Bit sampling.

Downlink compression performed by RCE (not instrument).

Parameter Table Version number.

Parameter Mode numbers.

To convert the two-character hex value to an integer, use the table below to find where the row matching the value's first character intersects with the column matching the second character. For example, the value "5B" is the integer 91.

Onboard processing type.

Onboard Processing Type Version. This supports scenario of multiple onboard processing versions of the same data telemetered to ground.

Sequence or Activity or Component identifier from command process.

If Sequence ID, composed of a 4-char subfield and a 5-digit numeric subfield representing the 6-bit “Category” and 14-bit numeric components of the commanded Sequence ID, respectively.

Identifier for the institution/team that created the product.

Identifies sequence ID or Round-Trip Tracking token (RTT).

Sequence-ID : Identifier indicating the command sequenced the image was acquired from. Specific values will be assigned by the uplink team.

RTT : Unique identifier used for tracking activities. Used in filename for PIXL only.

Note: All cameras will have an RTT associated with their images but not included in the filename. PIXL is a special case where RTT and PMC are required for filename uniqueness.

Product version number. In general, the highest number version represents the best version of a given product.

File extension; may be two, three, or four characters long.

Instrument identifier, as shown in the table below.

Instrument Configuration. Not used and set to "_".

Special Processing flag, applicable to RDRs only. Not used and set to "_".

Mission venue identifier.

Spacecraft Clock in second time unit, corresponding to the time the spectroscopy data was acquired by the instrument.

Underscore for readability.

Not used and set to "_".

Site identifier. Site location count from the RMC where the data were acquired.

Drive identifier. Drive count (position within a Site location) from the RMC where the data were acquired.

Instrument sequence-ID, the command sequenced of the spectroscopy or imaging measurement to be acquired. The first four characters are always SRLC. The remaining five characters are digits. The first digit after SRLC will always be 1 for spectral observations, and 0 for WATSON observations.

Instrument specific identifier.

Instrument specific identifier.

Instrument specific identifier.

Instrument specific identifier.

Identifier for the institution/team that created the product.

Product version number. In general, the highest number version represents the best version of a given product.

File extension; may be two, three, or four characters long.

Instrument identifier, as shown in the table below.

Underscore for readability.

Underscore for readability.

Spacecraft clock count, whole number of seconds

Underscore for readability.

Underscore for readability.

Underscore for readability.

Sequence number

Underscore for readability.

Name of target of observation, padded with underscores if needed

Underscore for readability.

Point number in raster, or 01 for single point

Identifier for the institution/team that created the product.

Product version number. In general, the highest number version represents the best version of a given product.

File extension; may be two, three, or four characters long.